Claude (Anthropic) End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Claude (Anthropic) versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Claude (Anthropic) Claude Opus 5.5 is supported until September 22, 2027, its end-of-support date. The next Claude (Anthropic) version to reach end of life is Claude Sonnet 4.5, on September 29, 2026. 19 of 33 tracked Claude (Anthropic) versions are past end of life; the most recent to reach it, Claude Opus 4.1, did so on August 5, 2026. The full Claude (Anthropic) lifecycle, with every version's release and end-of-support date, is in the table below.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| Claude 1.0 | — | Mar 14, 2023 | Nov 6, 2024 | 686 days past EOL | EOL |
| Claude Instant 1.0 | — | Mar 14, 2023 | Nov 6, 2024 | 686 days past EOL | EOL |
| Claude 1.1 | — | Mar 14, 2023 | Nov 6, 2024 | 686 days past EOL | EOL |
| Claude 1.2 | — | Mar 14, 2023 | Nov 6, 2024 | 686 days past EOL | EOL |
| Claude Instant 1.1 | — | Mar 31, 2023 | Nov 6, 2024 | 686 days past EOL | EOL |
| Claude 1.3 | — | Apr 18, 2023 | Nov 6, 2024 | 686 days past EOL | EOL |
| Claude 2.0 | — | Jul 11, 2023 | Jul 21, 2025 | 429 days past EOL | EOL |
| Claude Instant 1.2 | — | Aug 9, 2023 | Nov 6, 2024 | 686 days past EOL | EOL |
| Claude 2.1 | — | Nov 21, 2023 | Jul 21, 2025 | 429 days past EOL | EOL |
| Claude Sonnet 3 | — | Mar 4, 2024 | Jul 21, 2025 | 429 days past EOL | EOL |
| Claude Opus 3 | — | Mar 4, 2024 | Jan 5, 2026 | 261 days past EOL | EOL |
| Claude Haiku 3 | — | Mar 13, 2024 | Apr 20, 2026 | 156 days past EOL | EOL |
| Claude Sonnet 3.5 (20240620) | — | Jun 21, 2024 | Oct 28, 2025 | 330 days past EOL | EOL |
| Claude Sonnet 3.5 (20241022) | — | Oct 22, 2024 | Oct 28, 2025 | 330 days past EOL | EOL |
| Claude Haiku 3.5 | — | Oct 22, 2024 | Feb 19, 2026 | 216 days past EOL | EOL |
| Claude Sonnet 3.7 | — | Feb 24, 2025 | Feb 19, 2026 | 216 days past EOL | EOL |
| Claude Opus 4 | — | May 22, 2025 | Jun 15, 2026 | 100 days past EOL | EOL |
| Claude Sonnet 4 | — | May 22, 2025 | Jun 15, 2026 | 100 days past EOL | EOL |
| Claude Opus 4.1 | — | Aug 5, 2025 | Aug 5, 2026 | 49 days past EOL | EOL |
| Claude Sonnet 4.5 | — | Sep 29, 2025 | Sep 29, 2026 | 6 days remaining | Warning |
| Claude Haiku 4.5 | — | Oct 15, 2025 | Oct 15, 2026 | 22 days remaining | Warning |
| Claude Opus 4.5 | — | Nov 24, 2025 | Nov 24, 2026 | 62 days remaining | Warning |
| Claude Opus 4.6 | — | Feb 5, 2026 | Feb 5, 2027 | 135 days remaining | Warning |
| Claude Sonnet 4.6 | — | Feb 17, 2026 | Feb 17, 2027 | 147 days remaining | Warning |
| Claude Opus 4.7 | — | Apr 16, 2026 | Apr 16, 2027 | 205 days remaining | Active |
| Claude Opus 4.8 | — | May 28, 2026 | May 28, 2027 | 247 days remaining | Active |
| Claude Fable 5 | — | Jun 9, 2026 | Jun 9, 2027 | 259 days remaining | Active |
| Claude Mythos 5 | — | Jun 9, 2026 | Jun 9, 2027 | 259 days remaining | Active |
| Claude Sonnet 5 | — | Jun 30, 2026 | Jun 30, 2027 | 280 days remaining | Active |
| Claude Opus 5 | — | Jul 24, 2026 | Jul 24, 2027 | 304 days remaining | Active |
| Claude Fable 5.1 | — | Sep 1, 2026 | Sep 1, 2027 | 343 days remaining | Active |
| Claude Mythos 5.1 | — | Sep 1, 2026 | Sep 1, 2027 | 343 days remaining | Active |
| Claude Opus 5.5 | — | Sep 22, 2026 | Sep 22, 2027 | 364 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/claude)
Claude (Anthropic) lifecycle status — the real story
Anthropic publishes a four-stage lifecycle for Claude models: Active (fully supported and recommended), Legacy (no further updates, may be deprecated), Deprecated (still functional, not recommended, with a named replacement and a retirement date), and Retired (requests fail). Customers with active deployments get at least 60 days' notice before a publicly released model is retired, and the published table gives each active model a 'not sooner than' retirement floor.
The dates apply to Anthropic-operated platforms; Amazon Bedrock and Google Cloud set their own retirement schedules, so the same model can have a different status there. The end-of-life dates above are the published retirement dates and floors.
Verified against the vendor's lifecycle documentation on August 22, 2026.
Claude (Anthropic) release and support pattern
Of the 33 release lines tracked, 19 are past end of life and 14 are still within support. The newest line, claude-opus-5-5, was released September 22, 2026. The next scheduled end of life is claude-sonnet-4-5-20250929 on September 29, 2026 — 6 days from this build. The longest-supported line currently published is claude-opus-5-5, to September 22, 2027.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Claude (Anthropic) end of life mean for your organization?
When a version of Claude (Anthropic) reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Claude (Anthropic) should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Claude (Anthropic) reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Commercial extended support | Not available for Claude (Anthropic) from the original maintainer | Third-party vendors patch some end-of-life software on a custom basis; availability depends on the specific version and source access |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →